Autostart

When the vision controller is turned on, the Studio restores the state it was in when it was turned off. If a solution was deployed, the same solution is deployed again. The robot program can also check which solution is running and start or change it at any time. This page explains both. It applies to both Bin Picking Studio (BPS) and Locator Studio (LS).

In short: there is no autostart setting. The Studio remembers its last state, and the robot program decides which solution runs.

What happens when the vision controller starts

The Studio saves its state before the vision controller is turned off. When the vision controller is turned on again:

A solution was deployed when the vision controller was turned off – the same solution is deployed again automatically.
No solution was deployed – no solution is deployed. The Studio waits until a solution is started from the robot program or from the Studio.

Flowchart: after start-up the Studio deploys the last deployed solution, or nothing if no solution was deployed — What the Studio does when the vision controller is turned on.

When no solution is deployed, the Deployment page lists the solutions that can be deployed, each with a deploy button.

Deployment page with no solution deployed, listing solutions with deploy buttons — The **Deployment** page when no solution is deployed. Red frames: the page title and the **deploy** button of a solution.

On the Solutions page, the solution that was deployed last has the last run flag. Its tooltip says “This solution was last deployed.”

Solutions page row with the ready and last run flags — The **last run** flag (red frame) on the Solutions page. The solution name is blurred.

Starting the right solution from the robot program

To make sure the cell always runs the right solution after a restart, let the robot program check and set it when it starts. Three action requests do this:

Request	What it does	Works only when
Get running solution	Returns the ID of the solution that is deployed.	A solution is deployed.
Start solution	Deploys the solution with the given ID.	No solution is deployed.
Change solution	Stops the deployed solution and deploys the solution with the given ID.	A solution is deployed.

For Start solution and Change solution, the requested solution must be marked ready, and the robot brand of the solution must match the robot that sends the request. Both requests wait until the solution is deployed, an error occurs, or 180 seconds pass.

The recommended start-up of the robot program:

Connect to the vision controller (the Action Request Server).
Send Get running solution.
If no solution is running (the request returns an error), send Start solution with the ID of the wanted solution.
If a solution is running but it is not the wanted one, send Change solution with the ID of the wanted solution.
Continue with the robot program.

Flowchart of the robot program start-up with Get running solution, Start solution and Change solution — Recommended start-up logic of the robot program.

Warning: Always make sure the requested solution has the correct robot model selected.

For the parameters and responses of the requests, see Action requests.

Autostart in older versions

Bin Picking Studio 1.5.x and older had an Autostart flag: one solution could be marked to be deployed every time the vision controller started. Bin Picking Studio 1.6.0 replaced it with the automatic restore of the last state described above and with the requests to start a solution from the robot program at any time. Locator Studio works the same way.